Skip to content

fetch: start a stopped podman machine before loading the container - #71

Merged
paf0186 merged 1 commit into
lustre-tools:masterfrom
adilger:fetch-start-podman
Nov 16, 2026
Merged

paf0186 merged 1 commit into
lustre-tools:masterfrom
adilger:fetch-start-podman

Conversation

@adilger

@adilger adilger commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

ltvm target fetch and target publish took the podman usage lock but never ran the machine preflight that every build runs. So once the idle stop had stopped the macOS machine, half an hour after the last build, each fetch failed in podman load with "Cannot connect to Podman". A build started the machine again; a fetch never did.

Both now call check_podman_machine_macos(). It starts a stopped machine, repairs a wedged one and holds the usage lock, as for a build.

`ltvm target fetch` and `target publish` took the podman usage lock but
never ran the machine preflight that every build runs.  So once the idle
stop had stopped the macOS machine, half an hour after the last build,
each fetch failed in `podman load` with "Cannot connect to Podman".  A
build started the machine again; a fetch never did.

Both now call `check_podman_machine_macos()`.  It starts a stopped
machine, repairs a wedged one and holds the usage lock, as for a build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@paf0186
paf0186 merged commit fd431c0 into lustre-tools:master Nov 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants